Mobile tasks

ABSTRACT

Activities related to data analyses are managed in part using task objects representing tasks that need to be performed. In one embodiment, a method comprises: receiving a first request to generate a task object that describes a task; responsive to the first request, generating the task object, the task object being a data structure that comprises values for task object fields that represent attributes of the task; identifying, in a repository of data objects, a particular data object to associate with the task object; determining that a first field of the task object fields corresponds to a second field of the particular data object, the second field of the particular data object having a particular value; and assigning the first field of the task object to the particular value of the corresponding second field. In another embodiment, task objects are associated with geolocation data, and mapped or otherwise presented accordingly.

BENEFIT CLAIM

This application claims the benefit under 35 U.S.C. §120 as acontinuation of application Ser. No. 14/196,814, filed Mar. 4, 2014, theentire contents of which are hereby incorporated by reference as iffully set forth herein. The applicant(s) hereby rescind any disclaimerof claim scope in the parent application(s) or the prosecution historythereof and advise the USPTO that the claims in this application may bebroader than any claim in the parent application(s).

TECHNICAL FIELD

The present disclosure generally relates to data analysis.

BACKGROUND

The approaches described in this section are approaches that could bepursued, but not necessarily approaches that have been previouslyconceived or pursued. Therefore, unless otherwise indicated, it shouldnot be assumed that any of the approaches described in this sectionqualify as prior art merely by virtue of their inclusion in thissection.

Data analysis is a process of inspecting, cleaning, transforming, and/ormodeling data for objectives such as discovering useful information,suggesting conclusions, and/or supporting decision making. Various dataanalysis techniques involve repositories of data structures, such asdata objects, stored on computer-readable media. An object is typicallycomprised of named substructures, which are often referred to as fieldsor properties. In many repositories, objects may be interrelated basedon their properties and/or relationship data external to the objects.Two related objects are said to be associated, related, or linked.

Many repositories conform to one or more data models, ontologies,schemas, or other architectural frameworks, that place constraints onhow objects are organized. For example, in many repositories, objectsconform to one of a plurality of defined object types. Among otheraspects, the type of an object specifies which types of substructuresare found in the object. These substructures, referred to herein asproperties, are typically assigned property names.

Some computer-based tools for analyzing data allow an analyst tovisualize data objects in a variety of manners, or allow the analyst tomine, investigate, and/or take actions based upon the data objects. Forinstance, some types of data analysis tools allow an analyst to buildgraphs, charts, and/or reports based on various data objects. Anothertype of data analysis tool represents objects as linked nodes within agraph. Another type of data analysis tool involves workflows comprisinga series of action nodes that input one set of data objects and outputanother set of data objects.

In the course of analyzing data, a computer, analyst, or other entitymay determine that one or more actions need to be performed. Forexample, an analyst may determine that certain data objects are ofinterest for varying reasons, and that one or more actions need to beperformed to investigate and/or address those data objects.

For instance, many organizations utilize data analysis processes toconduct operations that include organization members performingactivities in a dispersed geographic area. The operations of a lawenforcement agency typically include police officers patrolling assignedgeographic areas, responding to crime scenes, and interviewing suspectsand witnesses. Or, a disaster relief organization may respond to anatural disaster by sending out aid workers to a disaster area to locateand provide assistance to those in crisis. These types of operations maybe referred to as field operations and may generally include monitoringspecific geographic areas and subjects, interacting with persons ofinterest, responding to and reporting information about the occurrenceof notable events, and any other activities that an organization membermay perform in the field. In order to better coordinate fieldoperations, an organization may employ one or more other organizationmembers at a centralized location, referred to herein as operationsanalysts, that help coordinate the activities of the organizationmembers in the field, referred to herein as field analysts. For example,operations analysts may be responsible for instructing field analysts onvarious actions or operations that need to be performed in view of adata analysis. Such actions or operations might include, for example,locations to investigate or subjects to monitor. Similarly, fieldanalysts may be expected to communicate certain information related tothe field operations back to operations analysts.

SUMMARY OF THE INVENTION

The appended claims may serve to summarize the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings:

FIG. 1 illustrates an example system in which the techniques describedherein may be practiced;

FIG. 2 illustrates an example flow for generating and utilizing alocation-sensitive task object;

FIG. 3 illustrates an example flow for assigning a task object fieldbased on an associated data object;

FIG. 4 illustrates an example interface for creating task objects and/orviewing information associated with existing task objects;

FIG. 5 illustrates an example mobile map interface;

FIG. 6 illustrates an example mobile task list interface for viewing alist of task objects;

FIG. 7 illustrates an example mobile task information interface forviewing information about a specific task object;

FIG. 8 illustrates another example mobile task information interface forviewing information about a specific task object;

FIG. 9 illustrates an example mobile interface in which informationabout task objects may be located;

FIG. 10 illustrates an example of a mobile data analysis system in whichthe techniques described herein may be practiced;

FIG. 11 illustrates an example mobile device system architecture;

FIG. 12 illustrates an example operations center architecture;

FIG. 13 illustrates a computer system upon which an embodiment may beimplemented.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of the present invention. It will be apparent, however,that the present invention may be practiced without these specificdetails. In other instances, well-known structures and devices are shownin block diagram form in order to avoid unnecessarily obscuring thepresent invention.

1.0. General Overview

According to various embodiments, activities related to data analysesare managed in part using task objects representing tasks that need tobe performed. According to an embodiment, a system comprises: a datarepository configured to store data objects; a task object generationcomponent, configured to generate task objects and cause the taskobjects to be stored in the data repository; an object linkingcomponent, configured to attach particular data objects stored in thedata repository to particular task objects generated by the task objectgeneration component; a data importing component, configured to identifya first field of a first task object, of the task objects, thatcorresponds to a second field of a first data object, of the dataobjects, the first data object having been attached to the first taskobject, the second field storing a particular value; wherein the dataimporting component is further configured to assign the first field ofthe first task object to the particular value of the second field of thefirst data object.

In an embodiment, the system further comprises a data updating componentconfigured to receive location input that identifies geographiclocations to associate with the task objects, and to store informationdescribing the geographic locations in association with the taskobjects. The system further comprises a data presentation componentconfigured to display task icons representing the task objects on a mapbased on the stored geographic locations.

In an embodiment, the first field and the second field are both one of:a location attribute, object title, object description, or assigned useror user group. In an embodiment, the task objects conform to a taskobject data structure type, the task object data structure type definingtask object fields of the task objects, including the first field. Thedata objects conform to particular data object structure types thatdefine particular fields of the data objects, the particular data objectstructure types being different from the task object data structuretype. The data importing component is configured to determine that thesecond field corresponds to the first field by comparing firstdefinition data for the task object data structure type to seconddefinition data for a first data object structure type to which thefirst data object conforms.

In an embodiment, the system further comprises a data updating componentconfigured to receive input indicating that tasks corresponding toparticular task objects have been completed. The data updating componentis configured to, responsive to input indicating that a first taskcorresponding to the first task object has been completed, and based onthe first task object being attached to the first data object,automatically change a status field of the first data object.

In an embodiment, the system further comprises: a data presentationcomponent configured to display, on a map, a plurality of task iconsrepresenting a plurality of the task objects that have not been assignedto user objects, of the data objects, and further configured to displaya plurality of user icons representing a plurality of the user objects;and an input handler configured to receive assignment inputs that dragparticular user icons over particular task icons; wherein the objectlinking component is configured to attach particular user objects,corresponding to the particular user icons, to particular task objects,corresponding to the particular task icons, responsive to the assignmentinputs received by the input handler.

In an embodiment, the system further comprises: a data presentationcomponent configured to display indications of distances between firstlocations associated with a plurality of the task objects and a secondlocation associated with a particular user object, of the data objects;wherein the object linking component is configured to, responsive toinput selecting a second task object from the plurality of the taskobjects, store an association between the second task object and theparticular user object.

In an embodiment, the system further comprises: a data updatingcomponent configured to determine that the first data object has beenupdated to store information describing a new geographic location; and adata presentation component configured to, responsive to the determiningthat the first data object has been updated, move a first icon thatrepresents the first task object to a new position on a map, the newposition reflecting the new geographic location.

According to an embodiment, a method comprises: receiving a firstrequest to generate a task object that describes a task; responsive tothe first request, generating the task object, the task object being adata structure that comprises values for task object fields thatrepresent attributes of the task; identifying, in a repository of dataobjects, a particular data object to associate with the task object;determining that a first field of the task object fields corresponds toa second field of the particular data object, the second field of theparticular data object having a particular value; and assigning thefirst field of the task object to the particular value of thecorresponding second field.

In an embodiment, the first field and the second field both represent alocation attribute, wherein the particular value is locationinformation. In an embodiment, the particular data object is one of: areport data structure, or an event data structure. In an embodiment, thefirst field and the second field are both an object title. In anembodiment, the first field and the second field are an assigned user oruser group. In an embodiment, the first request specifies an identifierfor the particular data object.

In an embodiment, the task object conforms to a task object datastructure type, the task object data structure type defining the taskobject fields. In an embodiment, the particular data object conforms toa particular data object structure type that defines particular fieldsof the particular data object, the particular data object structure typebeing different from the task object data structure type; anddetermining that the second field corresponds to the first fieldcomprises comparing first definition data for the task object datastructure type to second definition data for the particular data objectstructure type. In an embodiment, determining that the second fieldcorresponds to the first field comprises determining that the secondfield has a same name as the first field. In an embodiment, determiningthat the second field corresponds to the first field comprisesdetermining that the second field and the first field descend from acommon structural element of a common object type definition. In anembodiment, determining that the first field corresponds to the secondfield comprises: determining that the particular data object is of aparticular data object structure type; locating, in a plurality of datastructure type mappings, a mapping between the particular data objectstructure type and a task object data structure type; and determiningthat the first field corresponds to the second field based on themapping.

In an embodiment, the method further comprises assigning the first fieldof the task object to the particular value while generating the taskobject. In an embodiment, the method further comprises: receiving asecond request to attach the particular data object to the task object,and generating a link between the task object and the particular dataobject, wherein assigning the first field of the task object to theparticular value of the corresponding second field occurs responsive tothe second request. In an embodiment, assigning the first field of thetask object to the particular value comprises storing the particularvalue in the first field of the task object. In an embodiment, assigningthe first field of the task object to the particular value comprisesstoring a link between the first field of the task object and the secondfield of the particular data object. In an embodiment, assigning thefirst field of the task object to the particular value comprises,responsive to a second request to return the value of the first field ofthe task object: locating the particular data object based on a linkbetween the task object and the particular data object, and returningthe particular value in response to the second request based on thedetermining that the second field corresponds to the first field. In anembodiment, assigning the first field of the task object to theparticular value of the corresponding second field occurs onlyresponsive to determining that the first field of the task object isempty.

In an embodiment, the method further comprises assigning multiple valuesfor multiple fields of the task object fields based on values stored inthe particular data object. In an embodiment, the method furthercomprises identifying, in a repository of data objects, a secondparticular data object to associate with the task object; determiningthat a third field of the task object fields corresponds to a fourthfield of the second particular data object, the fourth field of thesecond particular data object having a second particular value; andassigning the third field of the task object to the second particularvalue of the corresponding fourth field.

In an embodiment, the method further comprises one or more of: changingthe particular value in the first field responsive to a change in theparticular value for the second field; and/or changing the particularvalue in the second field responsive to a change in the particular valuefor the first field. In an embodiment, the method further comprisesreceiving input indicating that the task corresponding to the taskobject is complete; and responsive to the input, based on theassociation between the task object and the particular data object,automatically changing a status field of the particular data object.

In an embodiment, the method further comprises: receiving input thatidentifies a geographic location to associate with the task object; anddetermining to associate the particular data object with the task objectbased on comparing the geographic location to one or more locationfields in the particular data object. In an embodiment, the methodfurther comprises displaying a first icon representing the task object;displaying a second icon representing the particular data object;receiving input that drags the second icon over the first icon; whereinidentifying the particular data object to associate with the task objectoccurs responsive to the input.

According to an embodiment, a method comprises: receiving a request togenerate a task object that describes a task; generating the task objectresponsive to the request; receiving first input that identifies ageographic location to associate with the task object; storinginformation describing the geographic location in association with thetask object; and displaying a first icon representing the task object ona map, based on the stored geographic location.

In an embodiment, the request specifies the geographic location. In anembodiment, the first input indicates a particular data object to attachto the task object, wherein the geographic location is stored in theparticular data object. In an embodiment, the first input indicates thata user has dragged the first icon to the geographic location on the map.In an embodiment, the method further comprises: displaying a second iconrepresenting a particular data object at the geographic location on themap, the particular data object storing the information describing thegeographic location; receiving second input that selects a graphicalinterface control associated with the second icon; wherein the requestis responsive to the second input, wherein the request thereby includesthe first input that identifies the geographic location.

In an embodiment, the method further comprises changing the first iconbased on a task status field of the task object. In an embodiment, thegeographic location is a first geographic location, and the methodfurther comprises: determining that the task object has been updated tostore a second geographic location that is not the first geographiclocation; and moving the first icon on the map to reflect the secondgeographic location. In an embodiment, the method further comprises:storing an association between the task object and a particular dataobject other than the task object, the particular data object storingthe information describing the geographic location; determining that theparticular data object has been updated to store information describinga new geographic location; and moving the first icon to a new positionon the map, the new position reflecting the new geographic location.

In an embodiment, the method further comprises: displaying, on the map,a plurality of task icons representing a plurality of task objects thathave not been assigned to user objects, the plurality of task iconsincluding the first icon; displaying a plurality of user iconsrepresenting the user objects; receiving input that drags a particularuser icon over the first icon; and storing an association between thetask object and a particular user object represented by the particularuser icon, the association indicating that the task object is assignedto the particular user object. In an embodiment, the method furthercomprises: displaying, on the map, a plurality of task iconsrepresenting a plurality of task objects that have not been assigned touser objects, the plurality of task icons including the first icon;displaying indications of distances between first locations associatedwith the plurality of task objects and a second location associated witha particular user object; responsive to input selecting the first icon,storing an association between the task object and the particular userobject, the association indicating that the task object is assigned tothe particular user object.

Other embodiments include, without limitation, a non-transitorycomputer-readable medium that includes processor-executable instructionsthat enable a processing unit to implement one or more aspects of thedisclosed methods as well as a system configured to implement one ormore aspects of the disclosed methods.

2.0. Structural Overview

FIG. 1 illustrates an example computer system 100 in which thetechniques described herein may be practiced, according to anembodiment. The various components of system 100 are implemented atleast partially by hardware at one or more computing devices, such asone or more hardware processors executing instructions, stored in one ormore computer-readable memories, for performing various functionsdescribed herein. System 100 is configured to store and manipulate datastructures in one or more data repositories 120. System 100 furthercomprises one or more output components 192 configured to cause outputdevices, such as computer monitors or printers, to display informationderived from the data structures. System 100 further comprises one ormore input handlers 193 configured to receive inputs that request tomanipulate the data structures stored in the one or more datarepositories 120 and/or the information displayed by the output devices.

In an embodiment, system 100 is a server computer system, comprising oneor more server computer devices that collectively implement the variouscomponents of system 100 as a set of server-side processes. The servercomputer system may include web server, application server, databaseserver, and/or other conventional server components that the depictedcomponents utilize to provide the described functionality. The outputcomponent(s) 192 send instructions that cause various client computingdevices, such as desktop computers or mobile computing devices, todisplay various presentations of data as described herein. For instance,the server computer system may output web pages and/or script-basedinstructions over any combination of network components to web browsersor other software applications at the client computing devices.Similarly, input handler(s) 193 receive inputs, such as hyper-texttransfer protocol (HTTP) requests or application programming interface(API) calls, from the client computing devices.

In an embodiment, system 100 is a “thick client” server-client system,in which certain components are implemented at a server computer systemas described above, while other components are implemented at clientcomputing devices such as described above. The exact division ofcomponents between the server computer system and the client computingdevices will vary depending on factors such as network speed andbandwidth and client computing resources. In such a system 100, outputcomponent(s) 192 communicate directly with display devices at the clientcomputing devices via, for instance, graphics APIs and/or command-lineinterfaces. Similarly, input handler(s) 193 receive inputs directly frominput devices such as touchscreens or keyboards. In yet otherembodiments, system 100 is a single computing device.

2.1. Data Repositories

System 100 comprises one or more repositories of data 120. The one ormore repositories of data 120 comprise computer-readable media thatpersistently store data for a variety of data structures, includingstructures referred to herein as objects. A data object is a datastructure that comprising values for various defined fields. Thesefields, also referred to as attributes or properties, reflect variousaspects of information modeled by a corresponding object type. Examplesof fields include, without limitation, titles, names, descriptions,dates, identifiers, categorical data, and so forth.

In an embodiment, a data object is a structure stored directly on acomputer-readable media. In other embodiments, a data object is alogical data structure described by various underlying structures storedon the computer-readable media. For instance, the values for a dataobject may be stored in a variety of underlying structure(s), such as afile, portions of one or more files, one or more XML elements, adatabase table row, a group of related database table rows, and soforth. An application will read the underlying structure(s), andinterpret the underlying structure(s) as the data object. The dataobject is then processed using various steps and algorithms such asdescribed herein.

In an embodiment, regardless of how the underlying data for an object isstored, a data server layer represents that underlying data to some orall of the other components of system 100 using object-oriented datarepresentation techniques, in accordance with one or more ontologies129. In yet other embodiments, no object-oriented data representationstechniques are necessary, and the components of system 100 utilizeobjects directly within their respective underlying data structureforms.

The one or more repositories 120 more specifically store at least taskobjects 121, geospatial objects 122, other data objects 123, andassociations 124. System 100 further comprises one or more ontologies129. An ontology 129 is a collection of definition data that describesvarious object types. Objects 121, 122, 123, 124 correspond to differentdiscrete object types defined by the one or more ontologies 129. In oneaspect, the one or more ontologies 129 define which fields are utilizedfor each object type. There may be multiple types of task objects 121,geospatial objects 122, other objects 123, and associations 124, each ofwhich may have their own individual object type definition in the one ormore ontologies 129.

Each task object 121 is a data structure that represents one or moretasks, which in turn correspond to a series of one or more actions thatneed to be performed. Data stored within the task objects describevarious aspects of the represented tasks, and may be presented usingmaps, graphs, and/or any other suitable presentation techniques. Basedon the task objects, interfaces may be provided that allow users toidentify tasks that need to be performed, identify locations at whichthe tasks need to performed, identify existing data objects within adata repository that are related to the tasks, track the progress of thetasks and/or various subelements of the tasks, report completion of thetasks to other users, and/or perform a variety of other actions relatedto the represented tasks.

Geospatial objects 122 include a variety of object types that include orare otherwise associated with location data describing one or moregeographic locations. Each geographic location may reflect, forinstance, a location at which a task is to be at least partiallyperformed, a location of a report or other data object in response towhich the task object was created, and/or a location of a user objectassigned to the task object. The degree of specificity of the geographiclocation may vary depending on the task object and/or the embodiment.For instance, a geographic location may be a coordinate within acoordinate system, such as a combination of a latitude, longitude,and/or elevation in a geographic coordinate system. The geographiclocation may instead be a physical address, including a street name andbuilding number, or the names of intersecting streets. The geographiclocation may instead be specified using a named place or region. Forinstance, the geographic location may be specified as any combination ofone or more of: a business name, pre-defined point of interest, city,zip code, state, country, and so forth. In an embodiment, the geographiclocation may be an arbitrary region having boundaries specified withrespect to any of the above, such as a radius from a specifiedcoordinate, a block bounded by a group of streets, or a polygon withspecified coordinates as vertices. In an embodiment, a task object maystore and/or be associated with information specifying a geographiclocation, and thus also be considered a geospatial object 122.

Other data objects 123 are not necessarily associated with locationdata. Both geospatial objects 122 and other data objects 123 may includea variety of types of objects. Example object types include eventobjects comprising data describing events that have occurred, reportobjects comprising data describing reports generated by users such asoperators or field analysts, user objects comprising data describingindividual persons, resource objects or asset objects comprising datadescribing physical assets or resources that are available, and soforth. In an embodiment, there may further be subcategories of the aboveobject types, for describing certain kinds of users, assets, resources,events, or reports that have a particular role or characteristic that isuncommon to other users, assets, resources, events, or reports. In anembodiment, any of the above objects may be assigned to group objects,so as to create, for instance, a team of users, or an inventory ofresources that belong to a particular user or department.

Associations 124 are data structures that describe relationships betweenobject 121-123. An association 124 may be a discrete data structure, oran association may be a logical construct derived from correlatingobjects 121-123 based on identifiers found in objects 121-123. Forinstance, one type of association is an attachment. A task object may,for instance, include a number of attachment fields specifyingidentifiers of other data objects 121-123 that have been attached to thetask object. Or, a separate association table may include records thatspecify a task object identifier for a task object, and another objectidentifier that corresponds to an object that has been attached to thetask object. Associations 124 may describe many other types ofrelationships to a given task object, such as an assigned user object,an allocated resource object, an originating report or event object, afollow-up task object, and so forth.

For simplification, this disclosure may at times refer to an object121-123 or other data structure within the one or more data repositories120 by referring to the task, report, user, or other item that the datastructure represents. Furthermore, examples of systems comprisingsuitable data repositories 120 are given in the documents incorporatedby reference in other sections of this application.

2.2. Task Object Generator

System 100 comprises a task object generation component 130. Task objectgeneration component 130 receives requests to generate task objects 121,and generates task objects 121 responsive to those requests. In responseto certain requests, task object generation component 130 may initiallygenerate “empty” task objects that comprise trivial or null values foreach task object field. In response to other requests, task objectgeneration component 130 may populate various fields of newly generatedtask objects 121 with values derived from parameters included with therequest or supplied by a data importing component 132.

Task object generation component 130 may provide one or more interfacesfor receiving requests to generate tasks, such as applicationprogramming interfaces (APIs) for receiving requests from othercomponents of system 100, including input handler 193. In an embodiment,task object generation component 130 may further provide to outputcomponent 192 various graphical user interface (GUI) elements forcreating new task objects. These elements may include controls such asbuttons, hot spots, icons, and so forth that guide a user in submitting,to input handlers 193, inputs that will be interpreted as requests togenerate new task objects 121. Example requests and interface elementsfor creating new task objects 121 are described in other sections.

2.3. Data Presentation Component

System 100 further comprises one or more data object presentationcomponents 140. Each data presentation component 140 generatespresentations of information based on data objects 121-124, such asgraphs, maps, charts, workflows, tables, reports, and so forth. Thepresentations are suited for a variety of analyses, including geospatialanalyses, relational analyses, and temporal analyses. System 100 mayfurther comprise map data that defines various aspects of maps that datapresentation component 140 may generate, such as address or coordinateinformation, points of interests, background map images, and so forth.Examples of systems comprising suitable data presentation components 140are given in the documents incorporated by reference in other sectionsof this application.

The presentations produced by data presentation component 140 areembedded in graphical user interfaces for viewing and/or manipulatingpresentations. These graphical user interfaces are then provided to anoutput component 192. The graphical interface may comprise, inadditional to the presentations, a variety of user interface controlsfor submitting inputs to input handler 193. Input handler(s) 193interpret the inputs as various commands to the components of system100. For instance, an input handler 193 may interpret some inputs ascommands for manipulating the presentations provided by datapresentation component 140, and thus send the commands to datapresentation component 140. Responsive to the commands, datapresentation component 140 reduces, expands, simplifies, filters, orotherwise manipulates the depicted presentations of objects andrelationships, in accordance with any suitable technique. Other examplesof user interface controls may include, without limitations, controlsfor selecting which presentation(s) and/or data objects 121-124 the datapresentation component 140 should display, controls for scrolling, zoomcontrols, and so forth.

2.4. Data Updater

System 100 further comprises one or more data updating components 195.Input handler(s) 193 may interpret other inputs as commands formanipulating data objects 121-124, and thus send the commands to a dataupdating component 195. The data updating component 195 then updates, orinstructs a data server component to update, data within the one or moredata repositories 120 in accordance to the commands.

In an embodiment, a data updating component 195 may further beconfigured to monitor various data objects 121-124 in accordance withconstructs referred to herein as triggers. A trigger is a set of one ormore instructions that are associated with specific objects 121-124, orfields thereof. When data updating component 195 changes a value in oneof the associated objects 121-124 or fields, or when data updatingcomponent 195 detects that a value has changed, data updating component195 executes the instructions in the trigger. One example of aninstruction that may be found in a trigger is an instruction to changeanother object 121-124, or field thereof, based on the changed value.For instance, a trigger may facilitate changing a task object 121 inresponse to a change in an object 123 that is associated with the taskobject 121, or vice versa.

A data updating component 195 may provide one or more interfaces forreceiving requests to update data, such as application programminginterfaces (APIs) for receiving requests from other components of system100, including input handler 193. In an embodiment, data updatingcomponent 195 may further provide to output component 192 various GUIelements for editing data objects 121-124. These elements may includecontrols such as text entry boxes, buttons, hot spots, icons, and soforth that guide a user in submitting, to input handlers 193, inputsthat will be interpreted as requests to update objects 121-124. Examplesof systems comprising suitable data updating components 195 are given inthe documents incorporated by reference in other sections of thisapplication

2.5. Object Linker

System 100 further comprises one or more object linking components 134.An object linking component 134 receives requests to associate two ormore of objects 121-123. Based on the requests, object linking component134 establishes associations 124. For instance, object linking component134 may receive a request to attach a specified object 122 or 123 to atask object 121. Object linking component 134 may therefore generate anassociation 124 between the specified object 122 or 123 and the taskobject 121. Optionally, object linking component 134 may furthergenerate metadata describing the association 124, such as an associationtype, date, and so forth.

In an embodiment, object linking component 134 further receives requestsfrom other components of system 100, such as data importing component132 or data presentation component 140, to locate objects 121-123 thatare associated with a specified one of objects 121-123. Object linkingcomponent 134 locates the associated objects 121-123 based on theassociations 124, and returns information identifying the associatedobject 121-123. In an embodiment, the requests may identify a specifictype of association 124 based upon which to locate the associatedobjects 121-123, and object linking component 134 may limit the responseto associated objects 121-123 having the specified type of association124.

An object linking component 134 may provide one or more interfaces forreceiving requests to establish associations 124 and/or retrieveassociated objects 121-123, such as application programming interfaces(APIs) for receiving requests from other components of system 100,including input handler 193. In an embodiment, data updating component195 may further provide to output component 192 various GUI elements forestablishing associations 124 and/or viewing associated objects 121-123.These elements may include controls such as text entry boxes, buttons,hot spots, icons, and so forth that guide a user in submitting, to inputhandlers 193, inputs that will be interpreted as requests to establishassociations 124 and/or generate presentations of associated objects121-123. Examples of such interfaces are given in other sections of thisapplication, as well as in the documents incorporated by reference inother sections of this application

2.6. Data Importer

System 100 further comprises a data importing component 132. Among otheraspects, data importing component 132 receives requests to assign datafrom an object 122 or 123 to a task object 121. Requests may bereceived, for instance, in response to object linking component 134establishing an association 124 between the object 122/123 and the taskobject 121. Requests may also or instead be received from an inputhandler 193 via interface controls configured to solicit inputs thatrequest performance of an import operation.

Data importing component 132 is configured to identify fields of a taskobject 121 that correspond to fields of an associated object 122/123.The identification process may involve, for instance, identifyingsimilar fields based on various metadata associated with the fields,such as names, descriptions, inherited features, and so forth. Forinstance, the identification process may involve consulting object typedefinitions in an ontology 129. The identification process may also orinstead involve consulting pre-defined mapping data that indicates whichfields of a particular object type correspond to which task objectfields. In an embodiment, data importing component 132 may employ anyother suitable technique for identifying fields that correspond betweenan object 122/123 and task object 121.

In an embodiment, data importing component 132 is configured to copyvalues from fields of objects 122/123 to corresponding fields of taskobject 121. In an embodiment, data importing component 132 is furtherconfigured to establish triggers that will cause data updating component195 to synchronize subsequent changes from one field of object 122/123or task object 121 to a corresponding field of object 122/123 or taskobject 121, so as to ensure that the two fields remain synchronizedbetween the object 122/123 and the task object 121. However, in otherembodiments, keeping the fields synchronized may not be desirable.

In an embodiment, data importing component 132 may further be called toassign data to a field of task object 121 dynamically, based on apreviously established association 124. Thus, rather than copying avalue from a field of an object 122/123 to a corresponding field of atask object 121, a link is established between the field of the taskobject 121 and the corresponding field of the object 122/123. When anycomponent of system 100 needs the value of the field of task object 121,data importing component 132 may be called to retrieve the value fromthe linked field of object 122/123.

2.7. Variations

System 100 illustrates only one of many possible arrangements ofcomponents configured to provide the functionality described herein.Other arrangements may include fewer, additional, or differentcomponents, and the division of work between the components may varydepending on the arrangement. For example, in other embodiments, thereneed not be geospatial objects 122 and/or other objects 123. In yetother embodiments, no object linking component 134, associations 124,and/or data importing component 132 are needed. In yet otherembodiments, associations 124 are established and maintained directly byother components of system 100, and no discrete object linking component134 is needed.

In FIG. 1, the various components of system 100 are depicted as beingcommunicatively coupled to various other components by arrows. Thesearrows illustrate only certain examples of information flows between thecomponents of system 100. Neither the direction of the arrows nor thelack of arrow lines between certain components should be interpreted asindicating the absence of communication between the certain components.Indeed, each component of system 100 may feature an open port, API, orother suitable communication interface by which the component may becomecommunicatively coupled to other components of system 100 as needed toaccomplish any of the functions of system 100 described herein.

3.0. Functional Overview

Techniques are described herein for generating and utilizing task dataobjects. The techniques described herein are performed by a system ofone or more computing devices, such as system 100 depicted in FIG. 1. Inan embodiment, each of the processes described in connection with thefunctional blocks described below may be implemented using one or morecomputer programs, other software elements, and/or digital logic in anyof a general-purpose computer or a special-purpose computer, whileperforming data retrieval, transformation, and storage operations thatinvolve interacting with and transforming the physical state of memoryof the computer.

3.1. Location-Sensitive Tasks

According to an embodiment, a user who has identified actions to performbased on data objects such as described herein may utilize the systemsand/or techniques described herein to create task objects that areassociated with location data. FIG. 2 illustrates an example flow 200for generating and utilizing a location-sensitive task object, accordingto an embodiment.

Block 210 comprises receiving a request to generate a task object thatdescribes a task. For example, an analyst or other user may access agraphical user interface that allows the user to create and view tasks.The graphical user interface may feature one or more controls that, whenselected by user input, cause the request to be sent to a task objectgeneration component, such as described elsewhere in this disclosure.The user may decide that a task object should be created, for instance,in response to viewing information from reports, events, or other dataobjects that indicate to the user that a task needs to be performed. Therequest may optionally include parameters that specify certain aspectsof the task, such as a title, description, due date, and so forth.

As another example, the request may be triggered programmatically inresponse to an automated process that analyzes various data objects anddetermines whether a certain condition has been met. For instance,various task triggers may be defined. Task triggers may be conditionedupon the lapsing of a certain time period, so that new tasks aregenerated automatically on a daily, weekly, or some other scheduledbasis. Task triggers may also or instead be conditioned upon findingthat one or more fields or one or more data objects have value(s) thatmeet certain specified criteria. When a particular set of one or moredata objects meet the conditions of a task trigger, the task triggersends a request to a task object generation component to create a taskobject. Various fields of the task objects may be assigned values thatare based on those found in the triggering data object(s). For instance,a task trigger may monitor data objects of a certain type for a certainstatus field value, such as “missing.” When the certain status fieldvalue is found in a data object, a task may be created with a title suchas “Find missing object” and a name that corresponds to the name of thedata object.

Block 215 comprises generating the task object responsive to therequest. A task object that conforms to a task object data structuretype is generated. The task object comprises values for task objectfields defined by the task object data structure type, such as a title,description, date due, and so forth. Depending on the embodiment, thevalues may be initially empty, or set to certain default values. In anembodiment, if parameters indicating values of the task object fieldswere included in the request of block 210, the parameters are storedwithin corresponding task object fields.

Block 220 comprises receiving first input that identifies a geographiclocation to associate with the task object. In an embodiment, therequest of block 210 includes the first input of block 220. Forinstance, the geographic location may be included as a parameter whenrequesting to creating the task object, or may be derived based on otherinformation included in or associated with the request. In otherembodiments, the geographic location may be added subsequent to therequest of block 210 via a task object property editing interface, aprogrammatic interface, or any other suitable data manipulationmechanism.

In an embodiment, the first input indicates a particular data object toattach to the task object. The geographic location is stored in one ormore fields of the particular data object, and is thus derived from theparticular data object. For instance, a user may request to create atask object that is attached to a certain report object or event objectthat already has an associated geographic location. The task object isautomatically associated with this same geographic location. Optionally,data from the particular data object may be linked to or imported intothe task object, as described in other sections.

In an embodiment, the first input indicates that a user has dragged atask icon to the geographic location on a map. For instance, responsiveto the request of block 210, a graphical user interface may display atask icon that represents the newly generated task object in aworkspace, graph, tree, list, or any other suitable display area. Thegraphical user interface may include a map display area. A user mayprovide the first input by clicking, tapping, or otherwise selecting thetask icon, and then dragging the task icon to the map display area. Theuser may then “drop” the task icon at a position in the map display areathat corresponds to the desired geographic location. In a similarembodiment, a task creation icon representing a process for creating anew task object may be displayed prior to block 210. The user may dragthe task creation icon to a position on the map display area to requestthat a new task object be created and associated with the geographiclocation that corresponds to the position.

In yet another embodiment, the graphical user interface may display anobject icon that represents a particular data object, such as a reportobject, event object, or user object, on the map. The particular dataobject stores information describing a geographic location, and is thusdisplayed at that geographic location. A user may drag and drop a taskicon or task creation icon on the object icon. Or, the user may select agraphical interface control associated with the second icon, such as byright-clicking on the object icon, or tapping on a button control whilethe object icon is in focus. Responsive this input, the graphical userinterface may create, or show a menu for creating, the task object atthe same geographic location as the particular data object. In anembodiment, the particular data object may furthermore be attached tothe task object, and/or data from the particular data object may belinked to or imported into the task object, as described in othersections.

Block 230 comprises storing information describing the geographiclocation in association with the task object. For instance, the taskobject may include one or more geographic location fields in whichinformation specifying the geographic location is stored. As anotherexample, a link between the task object and another object, such as theabove described particular data object, may be stored. Informationdescribing the geographic location may be stored, or may already bestored, within the other object. The geographic location is thusassociated with the task object via the link. In an embodiment, thegeographic location need not be stored in the exact same manner asprovided via the input of block 220, but rather may be converted orresolved to a different form prior to storage. For instance, if theinput of block 220 specified a predefined point of interest, block 230may comprise resolving the point of interest to a geographic coordinateor address. Similarly, if the input of block 220 specified a geographiccoordinate, the geographic coordinate may in some embodiments beresolved to an address prior to storage.

Block 240 comprises displaying a first icon representing the task objecton a map based on the stored geographic location. For instance, at sometime subsequent to block 230, a user may request to view the taskobject. In an embodiment, the user may specifically request to view thetask object stored in block 230. For instance, the user may search forthe task object or see the task object in a list of task objects. Theuser may then request to see the task object on a map. An iconrepresenting the task object is generated and displayed at a positioncorresponding to the geographic location stored in block 230. In anembodiment, the map may further include icons representing other dataobjects as well, such as user icons representing locations of userobjects, asset icons representing locations of asset objects, reporticons representing locations of report objects, and so forth.

In an embodiment, the user may request to view a group of task objectsthat happen to include the task object stored in block 230. A user mayrequest to view a variety of groups of task objects, including withoutlimitation a group of all task objects stored within a data repository,a group of task objects due by a certain date, a group of task objectswithin a certain proximity to a location, a group of unassigned taskobjects, a group of incomplete task objects, or a group of task objectswhose members are selected by filtering upon any other criteria that isbased upon data stored within or otherwise associated with a repositoryof task objects. Some or all of the task objects within the group maythen be presented as icons at their corresponding geographic locationswithin a map. The graphical user interface may further include controlsthat allow users to perform a variety of actions with respect to thetask objects depicted on the map, such as zooming into specific areas tobetter see the locations of certain task objects, filtering the group oftask objects, viewing a list of task objects, sorting the list of taskobjects by distance from a location or other criteria, selecting aspecific task object, or viewing and/or editing fields of a selectedtask object.

Optional block 250 comprises changing the task icon based on a taskstatus field of the task object. For instance, the task object may storea task status field whose value may be selected from an enumerated setof values, such as “not started,” “in progress,” or “complete.” Asanother example, a task status field may be set to a numerical valuerepresenting a percentage of the task that has been completed. Variousother types of task status fields may be stored. Depending on the valueof the task status field, the graphical user interface may display thetask icon differently. For example, different colors or sizes of taskicons may be used for different discrete values and/or ranges of valuesin a task status field. A red icon might therefore represent a task thathas not been started, while a green icon might represent a task that isin progress. As another example, entirely different task icons may beutilized to depict tasks objects, depending on the value of a taskstatus field.

In an embodiment, an icon may be customized based on the value of anyfield within a task object, regardless of whether the field is a taskstatus field. Moreover, a task icon may be customized based on multipletypes of fields within the same task object, and the graphical userinterface may modify the task icon differently for each field. Forinstance, different colors may be assigned based on a first task objectfield that indicates whether the task object has been started or iscomplete, while different icons sizes may be assigned based on a secondtask object field that indicates whether a task is currently assigned toa user.

Optional block 260 comprises moving the first icon on the map inresponse to determining that the task object is now associated with anew geographic location. For example, in some embodiments, a task objectis mobile. For example, re-assigning the location of a task object maybe necessary when a first element of a task has been completed at onelocation, but a field analyst determines that the next element must beperformed at another location. The task object may thus be assigned anew location using any suitable interface. Similarly, it may bedesirable to re-assign the location of a task object when the taskobject is attached to another mobile data object, such as a data objectused to represent a user, vehicle, or mobile asset. The attached dataobject may be updated based on, for instance, tracking logs from atracking device associated with the mobile data object. Based on atrigger associated with the attached data object and/or a link betweenthe task object and the attached data object, the task object is thusalso assigned to the new location.

Optional block 270 comprises storing an association between the taskobject and a particular user object. In an embodiment, the associationindicates that the task object is assigned to the particular userobject. A user corresponding to the particular user object may thus, forinstance, receive a message describing the task object, view the taskobject in a list or map of task objects currently assigned to the user,and/or update the task object in a task manipulation interface. However,other types of associations may also exist between task objects and userobjects. Moreover, in some embodiments, a task object may be associatedwith a group of user objects, such as a team object representing a teamof users.

In an embodiment, block 270 may comprise displaying, on the map, aplurality of task icons representing a plurality of task objects thathave not been assigned to user objects. Block 270 may further comprisedisplaying a plurality of user icons representing the user objects as alist of items, or in any other configuration, in an interface areaadjacent to the map. The graphical user interface receives input thatdrags a particular user icon over a task icon. Responsive to this input,an association is stored between the task object that corresponds to thetask icon and the user object represented by particular user icon.

In an embodiment, block 270 may comprise selecting a particular userobject. For example, the particular user object may correspond to acurrent user of the graphical user interface, or another user identifiedby the current user. A location of the particular user object isidentified or determined. Distances between the location and locationsassociated with task objects are determined. A list of task objects iscreated, sorted by distance from the particular user object. Or, a mapof the closest task objects to the particular user object is shown.Responsive to input selecting a particular task object in the graphicaluser interface, an association is stored between the particular taskobject corresponding and the particular user object.

Block 280 comprises receiving input indicating that a task associatedwith the task object is complete. For instance, a graphical userinterface for viewing and manipulating task objects may include controlsfor changing a task status field from an “in progress” or similar valueto “completed.” Block 290 comprises, responsive to the input of block280, updating the task object to have a status of complete.Consequently, the task object will no longer be presented in any displayof incomplete or in progress task objects.

Flow 200 is one example of a technique for generating and utilizing alocation-sensitive task object. Other flows may include fewer oradditional elements in varying arrangements. For example, in anembodiment, a task object may be associated with a plurality ofdifferent location fields indicating multiple locations associated withthe task object. Each location field may have a pre-defined oruser-configurable designation that indicates the significance of thelocation field. For instance, different locations may be associated withdifferent sub-elements of the task, and/or different attached objects. Amap interface may display a task object at all of its indicatedlocations, a currently active location, or a location having aparticular designation.

3.2. Tasks with Attachments

According to an embodiment, a user who has identified actions to performbased on data objects such as described herein may utilize the systemsand/or techniques described herein to create task objects that are“attached” or otherwise associated with other data objects. In anembodiment, certain task object fields may inherit, import, or otherwisebe assigned to values found in existing fields of associated dataobjects. FIG. 3 illustrates an example flow 300 for assigning a taskobject field based on an associated data object, according to anembodiment.

Block 310 comprises storing a repository of data objects, such asdescribed in other sections. Block 320 comprises receiving a firstrequest to generate a task object that describes a task, such asdescribed with respect to block 210. Block 330 comprises, responsive tothe first request, generating the task object, such as described withrespect to block 215.

Block 340 comprises identifying, in the repository of data objects, aparticular data object to associate with the task object. For instance,the particular data object may be a report object, event object, assetobject, user object, resource object, or any other suitable data object.

In an embodiment, the first request specifies an identifier for theparticular data object. For instance, while viewing informationassociated with the particular data object in a map, graph, or othersuitable presentation, the user may have selected a control forrequesting to create a task object that is associated with theparticular data object. A request that includes the identifier may havebeen generated and sent to a task object generation component. As partof generating the task object, the particular data object correspondingto the identifier is located. A link between the task object and theparticular data object may optionally be created.

In an embodiment, block 340 comprises receiving a second request toattach the particular data object to the task object, subsequent to thefirst request. For instance, a graphical user interface may display arepresentation of the task object. The graphical user interface may alsodisplay various representations of other data objects, such as a secondicon representing the particular data object. In response to receivinginput that drags the second icon over the representation of the taskobject, the second request may be generated, including an identifier forthe particular data object. A link between the task object and theparticular data object may optionally be created. As another example, amenu for editing fields of the task object may include an attachmentcontrol. Upon clicking or otherwise selecting the attachment control, auser may browse various data objects and select one or more data objectsto attach to the task object.

In an embodiment, block 340 comprises receiving input that identifies ageographic location to associate with the task object. In thisembodiment, block 340 further comprises determining to associate theparticular data object with the task object based on comparing thegeographic location to one or more location fields in the particulardata object. For instance, upon creating a location-sensitive taskobject per the techniques described in other sections, a task object mayautomatically be attached to the closest data object of a certain type,such as a user object or event object. In another embodiment, anassociation between the task object and the closest data object may besuggested via the graphical user interface. The user is given an optionto confirm the association.

Block 350 comprises determining that a first field of the task objectcorresponds to a second field of the particular data object. Forinstance, block 350 may involve determining that the second field has asame name as the first field. Or block 350 may comprise determining thatthe first field and the second field both represent a locationattribute, object title, assigned user, or assigned user group.

In some embodiments, the task object is of a task object data structuretype that comprises values for task object fields. The particular dataobject, meanwhile, conforms to a particular data object structure typethat defines particular fields of the particular object. Block 350 maythus comprise comparing first definition data for the task object datastructure type to second definition data for the particular data objectstructure type to identify similar fields. In an embodiment, block 350may comprise determining that the second field and the first fielddescend from a common structural element of a common object typedefinition. In an embodiment, predefined mappings of correspondingfields in different object types may be stored within the datarepository. Thus, block 350 may comprise locating, in a plurality ofdata structure type mappings, a mapping between the particular dataobject structure type and the task object data structure type, anddetermining that the first field corresponds to the second field basedon the mapping.

Block 360 comprises assigning the first field of the task object to thevalue of the corresponding second field. For instance, block 360 maycomprise copying the value of the corresponding second field to thefirst field of the task object while generating the task object and/orresponsive to the second request to attach the particular object to thetask object. In an embodiment, the first field may not necessarily storethe value of the corresponding second field, but rather be linked to thesecond field of the particular data object. Thus, when the value of thefirst field is requested, the value of the linked second field isreturned. In an embodiment, block 360 is only performed if the firstfield of the task object is empty, thus ensuring that no data isinadvertently overwritten. In other embodiments, however, it may bepreferred to overwrite the first field.

Block 370 comprises displaying a presentation of information based onthe task object. A task object may be depicted in varying forms in avariety of contexts, including as an icon or other component of a map,as an item in a list of task objects, as a node in a node-based graphthat interconnects the task object with other attached data objects, asa task progress report, and so forth.

Optional block 375 comprises updating the first field of the task objectresponsive to input that changes the value in the second field of theparticular data object. For instance, a trigger may be associated withthe second field, such that when the value of the second field changes,the value of the first field also changes. Alternatively, block 375comprises updating the second field of the particular data objectresponsive to input that changes the value in the first field of thetask object, in similar manner.

Block 380 comprises receiving input indicating that a task associatedwith the task object is complete, such as described with respect toblock 280. Block 390 comprises, responsive to the input of block 380,updating the task object to have a status of complete, such as describedwith respect to block 290.

Optional block 395 comprises, responsive to updating the task object inblock 390, updating one or more fields of the attached data object. Forinstance, a user may submit input indicating that the task correspondingto the task object is complete. Responsive to the input, and based onthe association between the task object and the particular object, astatus field of the particular object may be automatically updated to anew status, such as a “work order closed” status or other status.

Flow 300 is one example of a technique for assigning the value of a taskobject field based on an associated data object. Other flows may includefewer or additional elements in varying arrangements. For example, in anembodiment, a similar flow may be utilized to assign values to multiplefields of the task object, based on values stored in multiple fields ofthe particular data object. As another example, in an embodiment, asecond data object may be associated with the task object, and anotherfield of the task object may be assigned to a value from a correspondingfield of the second data object.

4.0. Example User Interfaces

The drawings discussed in this section are examples of the many types ofpresentations and interfaces that may be generated based on the dataobjects, systems, and/or techniques described herein. The informationand data objects depicted in these drawings are given by way of example.The interface techniques may be extended to any types of task objectsand data objects supported by the systems described herein. Otherinterfaces may include fewer, additional, or different elements invarying arrangements.

4.1. Example Task Creation/Editing Interface

FIG. 4 illustrates an example interface 400 for creating task objectsand/or viewing information associated with existing task objects,according to an embodiment. Interface 400 comprises a tab 410 forviewing a selected group of tasks. Additional tabs 410 for other groupsof tasks may be added using control 412. Interface 400 further comprisestask list 420 for selecting a task object for which to displayinformation in task information area 430. Task list 420 includes items422-426, each corresponding to a pre-existing task object.

Task information area 430 shows values from various fields of the taskobject whose list item 422-426 is selected in task list 420. Each of thevalues is shown in a field control 432-456 that also permits editing ofthe corresponding value. Each control 432-456 includes a labelindicating the name of the task object field that corresponds to thecontrol 432-456. Controls 432-456 include a status field control 432, anassigned user field control 434, a title field control 436, adescription field control 438, attachment field controls 440-444,location field controls 452, a creation timestamp field control 454, anda revision timestamp field control 456. Controls 454-456 are shaded ingray to indicate that the corresponding fields are not editable.

Attachment control area 440 lists all objects that have been attached tothe depicted task object. For each attached object, there is an attachedobject control 442. A user may launch a presentation of informationconcerning the attached object by selecting control. Attached objectcontrol 442 may further be deleted to remove the attachment from thetask object.

Attachment control area 440 further includes a control 444 for adding anew attachment. Over this control 444, a user may drag and drop an iconrepresenting another object from another interface area (not depicted),such as a graph, object list, or map. In response, the other object isattached to the task object. Alternatively, a user may click on control444 to browse other objects and locate a new object to attach. In anembodiment, upon attaching a new object via control 444, various fields432-438 and 452 are updated to include values from corresponding fieldsof the newly attached object, using techniques described in othersections. In an embodiment, fields 432-438 and 452 are updated in thismanner only if they are empty. In an embodiment, upon attaching a newobject, interface 400 will generate a prompt that asks the user if theuser wishes to import certain values from the newly attached object intocertain fields 432-438 and 452.

Interface 400 further includes a save control 490 that saves any changesmade to the task object via controls 432-456. Interface 400 furtherincludes a reversion control 480 that discards any changes made to thetask object via controls 432-456.

Above task list 420 is a task creation control 428. Upon selecting taskcreation control 428, the controls 432-456 are reset to empty or defaultvalues. Using controls 432-456, the user may assign values to varioustask object fields. The user may then click on control 490 to requestthat a new task object having the assigned values be created. A new item422-426 will then appear in task list 420, reflecting the newly createdtask object.

4.2. Example Mobile Interfaces

FIG. 5 illustrates an example mobile map interface 500, according to anembodiment. Map interface 500 comprises a map area 510 on which objecticons, including icons representing task objects and other data objects,may be depicted. Interface 500 includes an activated pull-down menu 520for accessing various data presentations, including a task control 530for accessing a presentation of task objects.

FIG. 6 illustrates an example mobile task list interface 600 for viewinga list of task objects, according to an embodiment. Interface 600comprises an inactive pull-down menu 610 that provides functionalitysimilar to pull-down menu 520. Interface 600 further comprises items620, each of which represents a different task object. Specifically,each item 620 includes a title of the respectively represented taskobject and a date of the respectively represented task object, which maybe a due date, revision date, or creation date, depending on theembodiment. For each item 620, there is a check box 630 for submittinginput indicating that the status field value of the respectivelyrepresented task object should be marked as “complete.” For each item620, there is also a control 640 for launching another interface forviewing more detailed information about the represented task object. Inan embodiment, items 620 have been filtered to include only task objectsthat are assigned to a user that has logged into the interface 600, or ateam to which the user is assigned. In other embodiments, there may bedifferent task interface screens 600 for different groups of taskobjects, including task objects assigned to different users or usergroups, unassigned task objects, task objects due within a certain timeperiod, tasks objects associated within a certain proximity to aspecific location, and so forth.

FIG. 7 illustrates an example mobile task information interface 700 forviewing information about a specific task object, according to anembodiment. Interface 700 comprises a pull-down menu 710 similar topull-down menu 610. Interface 700 further comprises a task title display720 that displays the value of a title field of a task object. Interface700 further includes other display elements for various fields of thetask object, including a description field display 731, attachment fielddisplay 732, location field display 733, creation date field display734, and revision date field display 735. Attachment field display 732includes a hyperlink for each attached object, by which a user mayrequest an interface for viewing more information about the assignedobject. Location field display 733 includes a hyperlink by which a usermay launch a map interface, such as map interface 500, centered upon thelocation associated with the task object.

Interface 700 further comprises a message notification area 790 thatalerts a user to the existence of a new task object or a newly assignedtask object. Message notification area 790 may be part of the sameapplication that displays the other components of interface 700, or maybe an overlay generated by an operating system or other messagingapplication. In an embodiment, a user may select message notificationarea 790 when it appears, in order to launch an interface 700 forviewing information about the new task object. In other embodiments,selecting message notification area 790 may launch other interfaces inwhich the new task object may be depicted, such as map interface 500 ortask list interface 600. In an embodiment, message notification area 790only appears when a new task object meeting certain criteria has beencreated. For instance, message notification area 790 may only appearwhen a task object is newly assigned to the user who is logged intointerface 700, or to a user group that includes the user. As anotherexample, message notification area 790 may also appear when anunassigned task object is located within a certain proximity of theuser's mobile device. The text in message notification area 790 may varydepending on the relationship between the new task object and the user.In an embodiment, a user may receive other new task notifications inaddition to or instead of that found in message notification area 790,such as via email or text message.

Interface 700 further includes a task completion checkbox 730 configuredfor submitting input that requests to mark the task object as complete.FIG. 8 illustrates another example mobile task information interface 800for viewing information about a specific task object, according to anembodiment. Interface 800 is the same as interface 700, except that taskcompletion checkbox 730 has been checked, and consequently aconfirmation message 810 is displayed asking the user to confirm whetherthe user intends to close the task object.

FIG. 9 illustrates an example mobile interface 900 in which informationabout task objects may be located, according to an embodiment. Interface900 comprises an asset object list 910. Items 931-933 of object list 910represent various asset objects. Items 931-933 are organized accordingto teams 920, and may further be organized by online/offline status. Auser may select one of items 931-933, and then click on a task button940. Upon clicking on the task button 940, a task list interface such asinterface 600 may appear, listing all task objects assigned or attachedto the asset object corresponding to the selected item 931-933. In otherembodiments, interface 900 may further comprise a task creation buttonconfigured to request creating a task that is attached to the selectedasset object. Similar interfaces 900 may exist for other types of dataobjects.

5.0. Example Mobile System Architecture

FIG. 10 illustrates an example of a mobile data analysis system 1000 inwhich the techniques described herein may be practiced, according to anembodiment. A mobile data analysis system 1000 generally facilitates thecommunication and the exchange of data between one or more mobiledevices (e.g., mobile devices 1006), one or more analyst workstations(e.g., analyst workstations 1014), and information stored in one or moredata repositories (e.g., data repositories 1010, 1018). The examplemobile data analysis system 1000 is conceptually described herein ascomprising a mobile device system 1002 supporting one or more mobiledevices 1006 and that is interconnected over a network 1012 to anoperations center system 1004 supporting one or more analystworkstations 1014 and other computing resources; however, the mobiledata analysis system 1000 represents just one system arrangement andother system arrangements are possible.

In an embodiment, a mobile device system 1002 comprises mobile devices1006, mobile device server 1008, and data repository 1010. Each ofmobile devices 1006 generally may comprise any mobile computing deviceincluding, without limitation, a smartphone, a cellular phone, a tablet,a laptop, and a personal digital assistant (PDA). Each of mobile devices1006 is communicatively coupled to mobile device server 1008 via one ormore wireless links that may include, for example, cellular, Wi-Fi,WiMAX, ZigBee, microwave, and other wireless network links. For thepurposes of illustrating a clear example, four mobile devices 1006 andone mobile device server 1008 are shown in FIG. 10, but practicalimplementations may use hundreds or thousands of mobile devices and anynumber of mobile devices servers.

In an embodiment, mobile device server 1008 may be communicativelycoupled to resources of operations center system 1004 via network 1012,which broadly represents one or more local area networks, wide areanetworks, global interconnected internetworks such as the publicinternet, or a combination thereof. Mobile device server 1008 generallymay be configured to coordinate communication between mobile devices1006 and resources of operations center system 1004 and to access andretrieve data stored in data repository 1010. For example, mobile deviceserver 1008 may be configured to relay search requests, messages, andother data sent from mobile devices 1006 to resources of operationscenter system 1004, and to send information received from operationscenter system 1004 to the appropriate mobile devices 1006.

In an embodiment, operations center system 1004 comprises one or moreanalyst workstations 1014, application server 1016, data repository1018, and web server 1020. One or more components of operations centersystem 1004 may, for example, be located in a centralized location thatis remote from mobile device system 1002 and mobile devices 1006.

In an embodiment, analyst workstations 1014 comprise one or moreworkstation computers, server computers, laptop computers, mobiledevices, or combinations thereof. Analyst workstations 1014 generallyare configured to support one or more operations analysts that mayrequest information provided by application server 1016 and/or webserver 1020, send information to application server 1016 to be stored indata repository 1018, communicate with one or more field analysts usingmobile devices 1006, and perform other operations described herein.

In an embodiment, application server 1016 generally is configured toaccess and retrieve data stored in data repository 1018 in response torequests from mobile devices 1006, mobile device server 1008, analystworkstations 1014, and web server 1020. Application server 1016 mayperform data manipulations and other operations in response to receivingrequests to access and/or store data in data repository 1018.

In an embodiment, data repository 1018 is the same as the one or morerepositories 120 of FIG. 1, while application server 1016 and web server1020 collectively implement other components of system 100. However, inother embodiments, the correspondence between the components of system100 and system 1000 may vary.

5.1. Mobile Device System Architecture

FIG. 11 illustrates an example mobile device system architecture 1100,according to an embodiment. In an embodiment, a mobile device systemarchitecture 1100 comprises one or more mobile devices 1006, mobiledevice server 1008, and data repository 1010.

In the embodiment illustrated in FIG. 11, a mobile device 1006, whichmay be implemented by one or more physical computing devices, iscommunicatively coupled to mobile device server 1008, which may beimplemented by one or more second physical computing devices, over oneor more wireless networks. A mobile device 1006 comprises a display1102, graphical user interface (GUI) logic 1104, mobile applicationlogic 1106, location sensors 1108, and camera 1110.

In an embodiment, GUI logic 1104 may be a set of program instructionswhich, when executed by one or more processors of a mobile device 1006,are operable to receive user input and to display a graphicalrepresentation of one or more graphic constructs related to the mobiledata analysis system approaches described herein. As an example, amobile device 1006 may be a smartphone and GUI logic 1104 may beoperable to receive touch screen signals and other user input from, anddisplay the graphics constructs to, a graphical user interface that isprovided on display 1102. Touch screen signals may comprise selectingbuttons, holding down buttons, selecting items displayed on the screen,dragging, or other gestures or selections. In general, GUI logic 1104 isconfigured to receive user input and determine what user requests orcommands are represented by the user input.

In an embodiment, a mobile device 1006 includes mobile application logic1106, which may comprise firmware, hardware, software, or a combinationthereof in various embodiments that is configured to implement thefunctions of a mobile data analysis system on a mobile device asdescribed herein. In one embodiment, mobile application logic 1106 maybe implemented as part of an application program configured to executeon the Android operating system. In other embodiments, mobileapplication logic 1106 may be implemented as a combination ofprogramming instructions written in any programming language (e.g., C++or Java) and hardware components (e.g. memory, CPU time) that have beenallocated for executing the program instructions on a mobile device1006.

In an embodiment, location sensors 1108 generally represent any sensorswhich may be used to determine information associated with a geographiclocation, spatial orientation, device movement, or any other informationassociated with the physical presence of a mobile device 1006, and whichmay be referred to herein as location data. Location data may include,for example, latitudinal and longitudinal coordinates, elevationmeasures, cardinal direction information, movement information, etc. Forexample, location sensors 1108 may comprise a Global Positioning System(GPS) component, motion sensors (e.g., an accelerometer), rotationsensors (e.g., a gyroscope), a compass, and a magnetometer. In anembodiment, mobile application logic 1106 is operable to receivelocation data from location sensors 1108 and to send the location datato a mobile device server 1008, which in turn may send the location datato resources of operations center system 1004. The receiving and sendingof location data by mobile application logic 1106 may be performedperiodically, at user configured intervals, or based on any otherschedule.

In an embodiment, camera 1110 generally represents any component capableof capturing multimedia information such as images, video, and sound.Camera 1110 may be integrated into a mobile device 1006 or may be anexternal device communicatively coupled to a mobile device 1006.

In an embodiment, mobile device server 1008 comprises mobile devicesecurity logic 1112 and repository access logic 1114.

In an embodiment, mobile device security logic 1112 provides processesfor controlling access to the mobile data analysis system by mobiledevices. For example, access by mobile devices 1006 to mobile deviceserver 1008, and via mobile device server 1008 to resources ofoperations center system 1004 over network 1012, may be restrictedand/or secured. As such, access by a mobile device user to a mobiledevice 1006 and/or mobile device server 1008 may be based on the usersupplying an authorized mobile device user account and associatedpasswords, secret questions, personal identification numbers (PINs),biometrics, and/or any other suitable authentication mechanism. Mobiledevice security logic 1112 comprise a set of program instructionsconfigured to process mobile device user login requests sent from amobile device 1006.

In one embodiment, user access to a mobile device 1006, mobile deviceserver 1008, and one or more of the resources of operations centersystem 1004 may be protected by separate authentication mechanisms. Inanother embodiment, mobile device security logic 1112 may be configuredto implement a Single Sign-On (SSO) access control system in order toprovide a single point of authentication for mobile device users. An SSOaccess control system generally enables a system resource, such asmobile device server 1008, to process access credentials supplied by amobile device user and, if a successful login occurs, to grant anauthenticated user account access to resources located on other systemresources, such as the resources of operations center system 1004, andwithout the mobile user manually authenticating with the other systems.

In an embodiment, communication between mobile devices 1006, mobiledevice server 1008, and resources in operations center system 1004 maybe secured using a cryptographic communication protocol such as, forexample, the Secure Sockets Layer (SSL) protocol. For example, each ofmobile devices 1006 may be configured for secure communications byinstalling a public key security certificate on the mobile devices and acorresponding private key security certificate on mobile device server1008 and resources of operations center system 1004. Mobile devicesecurity logic 1112 may comprise instructions configured to send andreceive encrypted network traffic based on the installed securitycertificates, whereby the mobile device security logic 1112 encodesoutgoing data with the public key security certificate, and mobiledevices server 1008 and/or resources of operations center system 1004decode received data with the installed private key securitycertificates.

In an embodiment, mobile device security logic 1112 may comprise programinstructions configured to restrict mobile device access to mobiledevice server 1008 based on a whitelist of authorized mobile devices. Amobile device whitelist may be configured by a mobile data analysissystem administrator and may include, for example, one or more entriesthat specify a unique identifier associated with approved mobiledevices. The unique identifier may be, for example, a device serialnumber, an international mobile equipment identity (IMEI) number, a MACaddress, or any other identifier that may be transmitted by a mobiledevice 1006 to mobile device server 1008. In an embodiment, mobiledevice security logic 1112 may be configured to cause mobile deviceserver 1008 to ignore requests that are sent from a mobile device thatdoes not supply an identifier on the whitelist. A mobile devicewhitelist may be stored in a database, a spreadsheet, or any othersuitable format for storage in a data repository such as data repository1010.

In an embodiment, mobile device server 1008 comprises repository accesslogic 1114. Repository access logic 1114 may comprise a set ofinstructions which, when executed by one or more processors, areoperable to access and retrieve data from data repository 1018. Forexample, repository access logic may be a database client or an OpenDatabase Connectivity (ODBC) client that supports calls to a databaseserver that manages data repository 1018.

In an embodiment, data repository 1010 generally represents any datastorage device (e.g., local memory on mobile device server 1008, sharedmemory, a database, etc.) known in the art which may be configured tostore data. In an embodiment, data repository 1010 may store, forexample, configuration files, security information, and other dataassociated with mobile devices 1006. In some embodiments, data stored indata repository 1010 may be accessed by mobile device server 1008 inorder to avoid sending requests for the same information to resources ofoperations center system 1004.

5.2. Operations Center System Architecture

FIG. 12 illustrates an example operations center architecture 1200,according to an embodiment. In an embodiment, operations centerarchitecture 1200 comprises application server 1016, web server 1020,and one or more analyst workstations, such as analyst workstation 1014.

In the embodiment illustrated in FIG. 12, analyst workstation 1014,which may be implemented by one or more physical computing devices, iscommunicatively connected to application server 1016 and web server1020, which may be implemented by one or more other physical computingdevices, over a network. In some embodiments, each such physicalcomputing device may be implemented as a separate computer system. Forexample, analyst workstation 1014 may be implemented in a computersystem as a set of program instructions recorded on a machine-readablestorage medium, while application server 1016 and web server 1020 may beimplemented in different computer systems.

Analyst workstation 1014 comprises graphical user interface (GUI) logic1204. GUI logic 1204 may be a set of program instructions which, whenexecuted by one or more processors of the computer system, are operableto receive user input and display a graphical representation of one ormore graphic constructs related to the mobile data analysis approachesdescribed herein. GUI logic 1204 may be operable to receive user inputfrom, and display the graphic constructs to, a graphical user interfacethat is provided on display 1202 by the computer system on which analystworkstation 1014 executes.

Analyst workstation 1014 may also interact with application server 1016to provide input, definition, editing instructions, and expressionsrelated to a mobile data analysis system as described herein using aprogrammatic interface, and then the application server 1016 may use,process, log, store, or otherwise interact with the received inputaccording to application server logic.

In an embodiment, web server 1020 is configured to provide one or moreweb-based interfaces to resources available from application server 1016and data repository 1018. As an example, one or more of mobile devices1006 may comprise a browser that can access HTML documents that webserver 1020 generates. The web pages may include information about datastored in data repository 1018. In other embodiments, web server 1020may use formats other than HTML for transmitting information torequesting devices.

In an embodiment, application server 1016 may be implemented as aspecial-purpose computer system having the logical elements shown inFIG. 12. In an embodiment, the logical elements may comprise programinstructions recorded on one or more machine-readable storage media.Alternatively, the logical elements may be implemented in hardware,firmware, or a combination.

When executed by one or more processors of the computer system, logic inapplication server 1016 is operable to perform mobile data analysissystem operations according to the techniques described herein. In oneembodiment, logic in application server 1016 may be implemented in aJava Virtual Machine (JVM) that is executing in a distributed ornon-distributed computer system. In other embodiments, logic inapplication server 1016 may be implemented as a combination ofprogramming instructions written in any programming language (e.g., C++or Visual Basic) and hardware components (e.g., memory, CPU time) thathave been allocated for executing the program instructions.

In an embodiment, application server 1016 comprises repository accesslogic 1214. Repository access logic 1214 may comprise a set ofinstructions which, when executed by one or more processors, areoperable to access and retrieve data from data repository 1018.

In an embodiment, data repository 1018 may be a type of structuredstorage for storing data including, but not limited to, relational orobject-oriented databases, data warehouses, directories, data files, andany other structured data storage. In one embodiment, data repository1018 is implemented as a revisioning database system configured to trackchanges made to data stored in the data repository. In an embodiment, arevisioning database system records metadata about changes to storeddata, facilitates UNDO and REDO operations of data changes, can receiverequests to subscribe to particular data and publish updates to suchdata for delivery to subscribers, and perform other functions.

In an embodiment, application server 1016 comprises mobile applicationbase logic 1206. Mobile application base logic 1206 generally includeslogic implementing mobile data analysis system operations that may berequested by an analyst workstation 1014 and mobile devices 1006 andcomprises mobile helper logic 1208 and geosearch logic 1210.

In an embodiment, mobile helper logic 1208 provides processes forassisting users to observe the location of various data objects inrepository 1018, such as one or more task objects or one or more objectsrepresenting mobile devices, on a map display. Mobile helper logicmobile device security logic 1112 may comprise program instructionsoperable to receive and store locational and other data sent from mobiledevices and to provide locational and other data in response torequests. The data received, stored, and sent may further includemetadata. Mobile helper logic 1208 may further comprise logic operableto transmit messages sent from mobile device and analyst workstationusers, perform data object searches, and other functionality describedherein.

In an embodiment, geosearch logic 1210 provides processes for handlinggeosearch requests sent from a mobile device and analyst workstationusers. In general, a geosearch request is a search request for dataobjects or other information that is associated with one or morespecified geographic locations or areas.

Systems 1000, 1100, and 1200, along with similar systems and techniquesthat utilize such systems, are described in greater detail in U.S.patent application Ser. No. 13/831,199, filed Mar. 14, 2013 and entitled“Mobile Reports,” the entire contents of which are hereby incorporatedby reference for all purposes as if set forth herein. Other examples ofsystems in which the described techniques may be utilized include,without limitation: U.S. patent application Ser. No. 12/840,673, filedJul. 21, 2010, U.S. patent application Ser. No. 13/247,987, filed Sep.28, 2011, and U.S. patent application Ser. No. 13/669,274, filed Nov. 5,2012. The entire contents of each of the above documents are herebyincorporated by reference for all purposes as if set forth in theirentirety herein.

6.0. Implementation Mechanisms—Hardware Overview

According to an embodiment, the techniques described herein areimplemented by one or more special-purpose computing devices. Thespecial-purpose computing devices may be hard-wired to perform thetechniques, or may include digital electronic devices such as one ormore application-specific integrated circuits (ASICs) or fieldprogrammable gate arrays (FPGAs) that are persistently programmed toperform the techniques, or may include one or more general purposehardware processors programmed to perform the techniques pursuant toprogram instructions in firmware, memory, other storage, or acombination. Such special-purpose computing devices may also combinecustom hard-wired logic, ASICs, or FPGAs with custom programming toaccomplish the techniques. The special-purpose computing devices may bedesktop computer systems, portable computer systems, handheld devices,networking devices or any other device that incorporates hard-wiredand/or program logic to implement the techniques.

For example, FIG. 13 is a block diagram that illustrates a computersystem 1300 upon which an embodiment may be implemented. Computer system1300 includes a bus 1302 or other communication mechanism forcommunicating information, and a hardware processor 1304 coupled withbus 1302 for processing information. Hardware processor 1304 may be, forexample, a general purpose microprocessor.

Computer system 1300 also includes a main memory 1306, such as a randomaccess memory (RAM) or other dynamic storage device, coupled to bus 1302for storing information and instructions to be executed by processor1304. Main memory 1306 also may be used for storing temporary variablesor other intermediate information during execution of instructions to beexecuted by processor 1304. Such instructions, when stored innon-transitory storage media accessible to processor 1304, rendercomputer system 1300 into a special-purpose machine that is customizedto perform the operations specified in the instructions.

Computer system 1300 further includes a read only memory (ROM) 1308 orother static storage device coupled to bus 1302 for storing staticinformation and instructions for processor 1304. A storage device 1310,such as a magnetic disk, optical disk, or solid-state drive is providedand coupled to bus 1302 for storing information and instructions.

Computer system 1300 may be coupled via bus 1302 to a display 1312, suchas a cathode ray tube (CRT), for displaying information to a computeruser. An input device 1314, including alphanumeric and other keys, iscoupled to bus 1302 for communicating information and command selectionsto processor 1304. Another type of user input device is cursor control1316, such as a mouse, a trackball, or cursor direction keys forcommunicating direction information and command selections to processor1304 and for controlling cursor movement on display 1312. This inputdevice typically has two degrees of freedom in two axes, a first axis(e.g., x) and a second axis (e.g., y), that allows the device to specifypositions in a plane.

Computer system 1300 may implement the techniques described herein usingcustomized hard-wired logic, one or more ASICs or FPGAs, firmware and/orprogram logic which in combination with the computer system causes orprograms computer system 1300 to be a special-purpose machine. Accordingto one embodiment, the techniques herein are performed by computersystem 1300 in response to processor 1304 executing one or moresequences of one or more instructions contained in main memory 1306.Such instructions may be read into main memory 1306 from another storagemedium, such as storage device 1310. Execution of the sequences ofinstructions contained in main memory 1306 causes processor 1304 toperform the process steps described herein. In alternative embodiments,hard-wired circuitry may be used in place of or in combination withsoftware instructions.

The term “storage media” as used herein refers to any non-transitorymedia that store data and/or instructions that cause a machine tooperate in a specific fashion. Such storage media may comprisenon-volatile media and/or volatile media. Non-volatile media includes,for example, optical disks, magnetic disks, or solid-state drives, suchas storage device 1310. Volatile media includes dynamic memory, such asmain memory 1306. Common forms of storage media include, for example, afloppy disk, a flexible disk, hard disk, solid-state drive, magnetictape, or any other magnetic data storage medium, a CD-ROM, any otheroptical data storage medium, any physical medium with patterns of holes,a RAM, a PROM, and EPROM, a FLASH-EPROM, NVRAM, any other memory chip orcartridge.

Storage media is distinct from but may be used in conjunction withtransmission media. Transmission media participates in transferringinformation between storage media. For example, transmission mediaincludes coaxial cables, copper wire and fiber optics, including thewires that comprise bus 1302. Transmission media can also take the formof acoustic or light waves, such as those generated during radio-waveand infra-red data communications.

Various forms of media may be involved in carrying one or more sequencesof one or more instructions to processor 1304 for execution. Forexample, the instructions may initially be carried on a magnetic disk orsolid-state drive of a remote computer. The remote computer can load theinstructions into its dynamic memory and send the instructions over atelephone line using a modem. A modem local to computer system 1300 canreceive the data on the telephone line and use an infra-red transmitterto convert the data to an infra-red signal. An infra-red detector canreceive the data carried in the infra-red signal and appropriatecircuitry can place the data on bus 1302. Bus 1302 carries the data tomain memory 1306, from which processor 1304 retrieves and executes theinstructions. The instructions received by main memory 1306 mayoptionally be stored on storage device 1310 either before or afterexecution by processor 1304.

Computer system 1300 also includes a communication interface 1318coupled to bus 1302. Communication interface 1318 provides a two-waydata communication coupling to a network link 1320 that is connected toa local network 1322. For example, communication interface 1318 may bean integrated services digital network (ISDN) card, cable modem,satellite modem, or a modem to provide a data communication connectionto a corresponding type of telephone line. As another example,communication interface 1318 may be a local area network (LAN) card toprovide a data communication connection to a compatible LAN. Wirelesslinks may also be implemented. In any such implementation, communicationinterface 1318 sends and receives electrical, electromagnetic or opticalsignals that carry digital data streams representing various types ofinformation.

Network link 1320 typically provides data communication through one ormore networks to other data devices. For example, network link 1320 mayprovide a connection through local network 1322 to a host computer 1324or to data equipment operated by an Internet Service Provider (ISP)1326. ISP 1326 in turn provides data communication services through theworld wide packet data communication network now commonly referred to asthe “Internet” 1328. Local network 1322 and Internet 1328 both useelectrical, electromagnetic or optical signals that carry digital datastreams. The signals through the various networks and the signals onnetwork link 1320 and through communication interface 1318, which carrythe digital data to and from computer system 1300, are example forms oftransmission media.

Computer system 1300 can send messages and receive data, includingprogram code, through the network(s), network link 1320 andcommunication interface 1318. In the Internet example, a server 1330might transmit a requested code for an application program throughInternet 1328, ISP 1326, local network 1322 and communication interface1318.

The received code may be executed by processor 1304 as it is received,and/or stored in storage device 1310, or other non-volatile storage forlater execution.

In the foregoing specification, embodiments have been described withreference to numerous specific details that may vary from implementationto implementation. The specification and drawings are, accordingly, tobe regarded in an illustrative rather than a restrictive sense. The soleand exclusive indicator of the scope of the embodiments, and what isintended by the applicants to be the scope of the embodiments, is theliteral and equivalent scope of the set of claims that issue from thisapplication, in the specific form in which such claims issue, includingany subsequent correction.

What is claimed is:
 1. A computer system comprising a data repositoryconfigured to store data objects; a task object generation component,implemented at least partially by computing hardware, configured togenerate task objects and cause the task objects to be stored in thedata repository; an object linking component, implemented at leastpartially by computing hardware, configured to attach particular dataobjects stored in the data repository to particular task objectsgenerated by the task object generation component; a data importingcomponent, implemented at least partially by computing hardware,configured to identify a first field of a first task object, of the taskobjects, that corresponds to a second field of a first data object, ofthe data objects, the first data object having been attached to thefirst task object, the second field storing a particular value; whereinthe data importing component is further configured to assign the firstfield of the first task object to the particular value of the secondfield of the first data object; a data updating component configured todetermine that the particular value in the first field of the taskobject has changed and, in response, update the particular value in thesecond field of the first data object.
 2. The system of claim 1, whereinthe first field and the second field are both one of: a locationattribute, object title, object description, or assigned user or usergroup.
 3. The system of claim 1: wherein the data updating component isconfigured to receive location input that identifies geographiclocations to associate with the task objects, and to store informationdescribing the geographic locations in association with the taskobjects; the system further comprising a data presentation componentconfigured to display task icons representing the task objects on a mapbased on the stored geographic locations.
 4. The system of claim 1,wherein the task objects conform to a task object data structure type,the task object data structure type defining task object fields of thetask objects, including the first field; wherein the data objectsconform to particular data object structure types that define particularfields of the data objects, the particular data object structure typesbeing different from the task object data structure type; wherein thedata importing component is configured to determine that the secondfield corresponds to the first field by comparing first definition datafor the task object data structure type to second definition data for afirst data object structure type to which the first data objectconforms.
 5. The system of claim 1, wherein the data updating componentis configured to: receive input indicating that tasks corresponding toparticular task objects have been completed; responsive to inputindicating that a first task corresponding to the first task object hasbeen completed, and based on the first task object being attached to thefirst data object, automatically change a status field of the first dataobject.
 6. The system of claim 1, further comprising: a datapresentation component configured to display, on a map, a plurality oftask icons representing a plurality of the task objects that have notbeen assigned to user objects, of the data objects, and furtherconfigured to display a plurality of user icons representing a pluralityof the user objects; an input handler configured to receive assignmentinputs that drags particular user icons over particular task icons;wherein the object linking component is configured to attach particularuser objects, corresponding to the particular user icons, to particulartask objects, corresponding to the particular task icons, responsive tothe assignment inputs received by the input handler.
 7. The system ofclaim 1, further comprising: a data presentation component configured todisplay indications of distances between first locations associated witha plurality of the task objects and a second location associated with aparticular user object, of the data objects; wherein the object linkingcomponent is configured to, responsive to input selecting a second taskobject from the plurality of the task objects, store an associationbetween the second task object and the particular user object.
 8. Thesystem of claim 1, wherein the data updating component is configured todetermine that the first data object has been updated to storeinformation describing a new geographic location; the system furthercomprising a data presentation component configured to, responsive tothe determining that the first data object has been updated, move afirst icon that represents the first task object to a new position on amap, the new position reflecting the new geographic location.
 9. Amethod comprising: receiving a first request to generate a task objectthat describes a task; responsive to the first request, generating thetask object, the task object being a data structure that comprisesvalues for task object fields that represent attributes of the task;identifying, in a repository of data objects, a particular data objectto associate with the task object; determining that a first field of thetask object fields corresponds to a second field of the particular dataobject, the second field of the particular data object having aparticular value; assigning the first field of the task object to theparticular value of the corresponding second field; wherein the methodis performed by one or more computing devices.
 10. The method of claim9, wherein the first field and the second field both represent alocation attribute, wherein the particular value is locationinformation.
 11. The method of claim 9, wherein the first field and thesecond field are both one of: an object title, object description, or anassigned user or user group.
 12. The method of claim 9, furthercomprising: receiving a second request to attach the particular dataobject to the task object; generating a link between the task object andthe particular data object; wherein assigning the first field of thetask object to the particular value of the corresponding second fieldoccurs responsive to the second request.
 13. The method of claim 9,wherein the task object conforms to a task object data structure type,the task object data structure type defining the task object fields;wherein the particular data object conforms to a particular data objectstructure type that defines particular fields of the particular dataobject, the particular data object structure type being different fromthe task object data structure type; wherein determining that the secondfield corresponds to the first field comprises comparing firstdefinition data for the task object data structure type to seconddefinition data for the particular data object structure type.
 14. Themethod of claim 9, further comprising: receiving input indicating thatthe task corresponding to the task object is complete; responsive to theinput, based on the association between the task object and theparticular data object, automatically changing a status field of theparticular data object.
 15. The method of claim 9, further comprising:identifying, in a repository of data objects, a second particular dataobject to associate with the task object; determining that a third fieldof the task object fields corresponds to a fourth field of the secondparticular data object, the fourth field of the second particular dataobject having a second particular value; assigning the third field ofthe task object to the second particular value of the correspondingfourth field.
 16. A method comprising: receiving a request to generate atask object that describes a task; generating the task object responsiveto the request; storing an association between the task object and aparticular data object, the particular data object storing differentdata than the task object; determining that a first field in the taskobject corresponds to a second field of the particular data object, thesecond field of the particular data object having a particular value;automatically copying the particular value of the corresponding secondfield to the first field of the task object; determining that theparticular value in the first field of the task object has changed and,in response, updating the particular value in the second field of thefirst data object; wherein the method is performed by one or morecomputing devices.
 17. The method of claim 16, further comprising:receiving first input that identifies a first geographic location toassociate with the task object; storing information describing the firstgeographic location in association with the task object; displaying afirst icon representing the task object on a geographic map, the firsticon placed on the geographic map at a point that corresponds to thestored first geographic location of the task object; determining thatthe task object has been updated to store a second geographic locationthat is not the first geographic location; moving the first icon on themap to reflect the second geographic location.
 18. The method of claim16, further comprising: displaying, on a map, a plurality of task iconsrepresenting a plurality of task objects that have not been assigned touser objects, the plurality of task icons including a first iconassociated with the task object; displaying a plurality of user iconsrepresenting the user objects; receiving input that drags a particularuser icon over the first icon; storing an association between the taskobject and a particular user object represented by the particular usericon, the association indicating that the task object is assigned to theparticular user object.
 19. The method of claim 16, further comprising:displaying, on the map, a plurality of task icons representing aplurality of task objects that have not been assigned to user objects,the plurality of task icons including a first icon associated with thetask object; displaying indications of distances between first locationsassociated with the plurality of the task objects and a second locationassociated with a particular user object; responsive to input selectingthe first icon, storing an association between the task object and theparticular user object, the association indicating that the task objectis assigned to the particular user object.